ci: add post-release check workflow [ED-25263] - #49
Merged
Conversation
Automate published-artifact verification and an upgrade-path editor smoke so post-release checklist items are not manual. Co-authored-by: Cursor <cursoragent@cursor.com>
Wiz Scan Summary
To detect these findings earlier in the dev lifecycle, try the Wiz Code extension for VS Code, JetBrains, or Visual Studio. |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Uninstall before installing the released zip so WP-CLI does not force-update a live Elementor tree, commit lockfile-driven action bundles, and tighten zip/summary handling for CodeQL. Co-authored-by: Cursor <cursoragent@cursor.com>
gitstream-cm
Bot
added
🚨 2 Unresolved Thread(s)
and removed
🚨 2 Unresolved Thread(s)
labels
Checkout this repo when the workflow is reused, so Core/Pro do not run against their own tree. Fail the editor-edit smoke if EXISTING_PAGE_ID is missing. Co-authored-by: Cursor <cursoragent@cursor.com>
4 tasks
Refuse Core downgrades, fail clearly when the token cannot read Pro, enforce required Core, and pin reusable checkout to the caller ref. Co-authored-by: Cursor <cursoragent@cursor.com>
DTS build failed TS2532 on split/index access. Guard the prerelease split and version-part lookups so turbo build can complete. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Beta tags like 4.3.0-beta2 have no changelog on main. Co-authored-by: Cursor <cursoragent@cursor.com>
PHP 8.0 wp-env images still run apt-get on Debian bullseye, which currently fails when bullseye-security InRelease is stale. Co-authored-by: Cursor <cursoragent@cursor.com>
Debian bullseye-security currently 404s package debs after apt-get update. Bookworm-based WordPress PHP 8.2 images avoid that, and apt installs skip upgrades if an old image is still used. Co-authored-by: Cursor <cursoragent@cursor.com>
Lighthouse and setup-elementor-env source did not change; restore their bundles from main. Co-authored-by: Cursor <cursoragent@cursor.com>
…263] PR runs checked live published Core, not the branch, and were a weak expensive gate. Co-authored-by: Cursor <cursoragent@cursor.com>
Callers must pass the same ref as the uses: pin so YAML and ./actions cannot drift. Copy dispatch input help onto the reusable contract. Co-authored-by: Cursor <cursoragent@cursor.com>
Avoid a Core-only upgrade green when Pro was in the call. Assert zip filenames after download. Co-authored-by: Cursor <cursoragent@cursor.com>
Verify gates are exercised on dispatch and Core/Pro callers. Changelog and header parsers stay covered in editor-github-actions-utils. Co-authored-by: Cursor <cursoragent@cursor.com>
CI rebuilds lighthouse and setup-elementor-env bundles even when their sources did not change. Co-authored-by: Cursor <cursoragent@cursor.com>
Svitlana-Dykun
changed the title
The action bundle options were identical. Avoid another copy of tsup.config.ts on this PR. Co-authored-by: Cursor <cursoragent@cursor.com>
Svitlana-Dykun
changed the title
davseve
approved these changes
Sep 10, 2026
Svitlana-Dykun
added a commit
to elementor/elementor
that referenced
this pull request
Sep 10, 2026
## Summary - Adds a dispatchable **Post-Release Check** workflow in Core that calls the reusable workflow in `elementor-editor-github-actions`. - Runs published-artifact verify (GitHub release, changelog on `main`, wordpress.org SVN, zip headers) plus editor upgrade smoke after a GA. https://elementor.atlassian.net/browse/ED-25263 Depends on elementor/elementor-editor-github-actions#49 (currently pinned to `feat/post-release-check`; switch `uses` and `actions_ref` to `@main` after that PR merges). ## Test plan - [ ] Merge or have access to `elementor-editor-github-actions` branch `feat/post-release-check`. - [ ] Confirm this repo can use reusable workflows from that repository (org Actions access). - [ ] Actions → **Post-Release Check** → Run workflow with a published Core version (e.g. `4.2.3`), Pro empty. - [ ] Confirm verify + smoke jobs run in the called workflow and `MAINTAIN_TOKEN` is available if Pro is passed. Made with [Cursor](https://cursor.com) <!--start_gitstream_placeholder--> ### ✨ PR Description ## 1. Problem & Context Implements a caller workflow for ED-25263 to trigger post-release validation via a reusable GitHub Action. ## 2. What Changed (Where) - `.github/workflows/post-release-check.yml`: New workflow to call the reusable post-release check action. ## 3. How It Works Manual dispatch triggers the workflow, passing versioning and skip flags to the remote reusable workflow. _Generated by LinearB AI and added by gitStream._ <sub>AI-generated content may contain inaccuracies. Please verify before using. 💡 **Tip:** You can customize your AI Description using **Guidelines** [Learn how](https://docs.gitstream.cm/automation-actions/#describe-changes)</sub> <!--end_gitstream_placeholder--> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
main, wordpress.org SVN/Stable tag, and zip version headers for published Core (and optional Pro).plugin-upgrade-test.yml): install current wordpress.org Elementor, import a heading page,--forceinstall the released zip, then Playwright for frontend + create/edit canvas.https://elementor.atlassian.net/browse/ED-25263
Test plan
core_version=4.2.2(Pro empty) and confirm the job summary checklist is green.MAINTAIN_TOKENcan readelementor/elementor-proreleases.Made with Cursor
✨ PR Description
1. Problem & Context
Implements a post-release verification suite ED-25263 to automate the validation of published Core and Pro artifacts, ensuring version consistency and basic editor stability after a release.
2. What Changed (Where)
.github/workflows/post-release-check.ymlactions/post-release-verifyactions/post-release-smokeactions/setup-wp-envapt-getto bypass Debian Release expiry failures.packages/editor-github-actions-utils3. How It Works
The workflow resolves versions$\rightarrow$ $\rightarrow$
post-release-verifychecks GitHub releases and zip headerspost-release-smokeinstalls the released zip over a live.orgsite and runs Playwright editor tests.4. Risks
MAINTAIN_TOKENto access private Pro repos; missing tokens will fail verification.skip-wordpress-orginput.Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how